The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / bbs / fn397c_1.zip / README.NOW < prev next >

Wrap

Text File | 1991-12-13 | 26KB | 717 lines

---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.97c 12 December 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace / add / edit the following files: fnet.exe ; replace fncfg.exe ; replace fncfg.ndx ; replace fncfg.hlp ; replace fnetsm.exe ; replace fnchk.exe ; replace fnchk.cfg ; edit as indicated in fnet.doc (changed in version 3.97c) fnettext ; replace or edit with fntext.com fnetprot.dat ; replace or edit your OLD file to reflect the additions ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.97b 25 November 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace / add the following files: fnet.exe fncfg.exe fncfg.ndx fncfg.hlp 3. If you desire to configure your 'fnetprot.dat' file for the HS/Link bi-directional protocol use the letter "H" for the keyword for it. FeatherNet version 4.0 will have a means of specifying whether any protocol is bi-directional or not. ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.97a 17 November 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace / add the following files: fnet.exe fncfg.exe fncfg.ndx fncfg.hlp fnetsm.exe fnettext (Use the 'fntext.com' program and the changes in the 'fntext' file to update your "custom" fnettext file.) ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.97 03 November 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace / add the following files: fnet.exe fncfg.exe fncfg.ndx fncfg.hlp fnetsm.exe fnfiler.exe fnchk.exe fnchk.cfg (each node dir) fnfiler.cfg (each node dir) fnettext fnettest.bat (each node dir) fnvisual.hlp (bbs home dir) 3. Run fncfg.exe and save the configuration with the "Y" option. 4. Read 'fnread.me' regarding the changes/additions/fixes. ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.96 05 September 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace the following files: fnet.exe fncfg.exe fnetsm.exe 3. Run fncfg.exe and save the configuration with the "Y" option. 4. Read 'fnread.me' regarding the changes/additions/fixes. ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.95 30 August 91 1. Ensure you have a backup of your bbs home directory and all node directories. 2. Replace the following files: fnet.exe fncfg.exe fnetsm.exe fnchk.exe cname.exe localup.exe 3. Run fncfg.exe and save the configuration with the "Y" option. 4. Read the documentation (fnet.doc) regarding the changes/additions mentioned in 'fnread.me'. 5. Edit the 'fnettest.bat' file to meet your needs (testing uploads with some external program such as AC or ZipLab). 6. Edit the FNCHK.CFG file to meet your needs/desires. 7. This completes the upgrade to version 3.95 8. Call 619-446-4505 / 4506 and D/L 'fnmailxx.zip' - FeatherNet .QWK Mail Door ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.h 01 AUgust 91 1. Ensure you have a backup of your bbs home directory and any node directory. 2. Replace the following files: fnet.exe fncfg.exe fnetsm.exe fnchk.exe 3. Run fncfg.exe and save the configuration with the "Q" option. 4. This completes the upgrade to version 3.9h ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.9g 14 July 1991 1. Ensure you have a backup of your bbs home directory and any node directory. 2. Replace the following files: fnet.exe fncfg.exe fnetsm.exe 3. Run fncfg.exe and save the configuration with the "Q" option. 4. This completes the upgrade to version 3.9g ---------------------------------------------------------------------------- - Note - - ---- - - If you are NOT upgrading from a previous version of Feathernet - - do not read any further! - ---------------------------------------------------------------------------- U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.9f 15 June 1991 1. Ensure you have a backup of your bbs home directory and any node directory. 2. Replace the following files: dirndx.exe fnet.exe fncfg.exe fnetsm.exe fnchk.exe privpack.com privutil.exe 3. Run fncfg.exe and save the configuration with the "Y" option. 4. This completes the upgrade to version 3.9f ------------------------------------------------------------------------------ U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.9e 14 May 1991 Perform the following steps to upgrade to version 3.9e from version 3.9d. 1. Make backups of these files: fnet.exe fncfg.exe fncfg.ndx fncfg.hlp fnetsm.exe srconfig sigdata dirdata dirmast fnchk.exe 2. Unzip the archive(s) and overwrite these files: fnet.exe fncfg.exe fncfg.hlp fncfg.ndx fnetsm.exe fnchk.exe 3. Ensure the following files are also unarchived and are placed in the dos file path: dndxcfg.exe dirndx.exe privutil.exe privpack.com 4. Ensure you run 'fncfg.exe' and verify all the conference, file directory and other information. 5. This completes the upgrade. ------------------------------------------------------------------------------ U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.9d 27 April 1991 Perform the following steps to upgrade to version 3.9d from version 3.9c. 1. Make backups of these files: srconfig fncfg.hlp fncfg.ndx 2. Unzip the archive(s) and overwrite these files: fnet.exe fncfg.exe fncfg.hlp fncfg.ndx fnfiler.exe 3. Run fncfg.exe and answer the security level required to change the directory control file (if you have more than one). Save the configuration. 4. If you have more than one directory control file make two menu files (dmas.men and dmasg.men) which is displayed when the "C" command is entered from the file transfer area to change directory control files. 5. This completes the upgrade. ------------------------------------------------------------------------------ U P G R A D E N O T I C E --------------------------- Feathernet Bulletin Board Version 3.9c 17 April 1991 Perform the following steps to upgrade to version 3.9c from version 3.9, 3.9a or 3.9b. 1. Make backups of these files: sigdata srconfig fnextusr (if present) users 2. From the bbs NODE directory run the file 'sig39c.exe'. This modifies the 'sigdata' file with your assistance to define the public and private conferences. New callers will be given access to ALL public conferences that the NEW USER security level is equal or greater than. 3. From any NODE directory (where the 'srconfig' file resides) run the program 'fext.exe'. This modifies the 'fnextusr' file to support some changes in the way Feathernet handles conference registration information. 4. Run the program 'fncfg.exe' from the NODE directory and save the configuration. This completes the upgrade to version 3.9c. ----------------------------------------------------------------------------- Ensure you run 'fncfg.exe' and save the configuration prior to attempting to run version 3.9 release code. ----------------------------------------------------------------------------- These upgrade instructions are in a descending order. Ensure you are upgrading from one version to the VERY NEXT release. Then proceed to the next NEWER upgrade instruction. In other words, begin at the END of this file and work towards the beginning, bypassing all instructions already complied with. ----------------------------------------------------------------------------- Feathernet Bulletin Board Version 3.9 10 April 1991 o Fixed a bug in message Quoting which was placing the wrong initials into the Quoted part of a message. o Fixed a bug in the routine to read the (P)revious message. It now works properly. o Added support for the @Xbf (b=Background f=Foreground) color codes as substitute for ansi codes in menus and text files. Feathernet will ignore these codes if the use is not ansi capable. The color codes are: @Xbf, where b is background and f is foreground. Low intensity: 0 = black 1 = blue 2 = green 3 = cyan 4 = red 5 = magenta 6 = yellow 7 = white High Intensity: 8 = black 9 = blue A = green B = cyan C = red D = magenta E = yellow F = white Blinking (Note: only applicable as a background.): 8 = black 9 = blue A = green B = cyan C = red D = magenta E = yellow F = white Note 1: Caps lock should be down when using this format. Note 2: Blinking Background is not supported by Feathernet. Here is an example: @XDF Hello This produces a white Hello on a blinking magenta background. ----------------------------------------------------------------------------- Feathernet Bulletin Board Version 3.9jß 17 March 1991 I N F O R M A T I O N --------------------- o Optimized the code considerably and have reduced the size of the program by approximately 7K while adding several routines. o Changed the 'dirmast' file format in order to support the new file directory listing "menu" files. These files are ascii and ansi text file the sysop must create with a text editor/ansi editor/utility program which will list the various file directories available within each directory control area. The ANSI version will have a "G" appended by Feathernet when ansi is toggled on in the bbs. Thus, there is a REQUIREMENT that the names of these directory "menu" files be limited to seven (7) characters with no file extension (.xxx) permitted. (Running the utility A sample dirmast file for version 3.9jß follows: --------------- 3 dirlist1 g:\qb3\dirm1 dirlist2 g:\qb3\dirm2 dirlist3 g:\qb3\dirm3 ---------------- Note the ability to specify the file directory the directory listing "menu" file is located in. Feathernet will soon allow paths to be specified for most files used within the bbs. Many sysops have asked for this and it is being worked on now. o Corrected some display problems with several text files. o Modified the 'Waiting for Call' screen to correct a potential minor problem which causes a colored square on the screen after the top status line when a caller is online. o Corrected some problems with the caller.log writing routine which caused the records in the log to be displayed incorrectly by the internal caller log viewing routine. Upgrading --------- 1. Ensure you have backed up all system files and the fncfg.exe and fnet.exe files from the previously installed version! 2. Due to the change in the 'dirmast' file directory control file structure yet another utility has been created. Its name is 'dirmast.exe'' This utility *MUST* be run prior to running 'fncfg.exe' or running the bbs. It should be run *ONLY* once within EACH node directory. It's purpose is to update the 'dirmast' file with the version 3.9jß file format. 3. Unzip 'fn39j.ZIP' in each NODE directory. Copy 'fnettext' to the HOME directory (where all 'DIRxx' files reside) if the HOME directory is not also the NODE directory. Over the following files: fnet.exe fncfg.exe fnet.scr 4. Ensure you have run 'dirmast.exe' from each NODE directory. Now use a text editor to edit the path and name of each directory list 'menu' file name in the file 'dirmast' (located in each NODE directory). The program 'dirmast.exe' names these menu files in the following way: The NODE directory path plus the name "DIRM" plus the number of the directory control entry. Assuming the bbs NODE directory is "C:\FNET" the first entry's menu file will be named "C:\FNET'DIRM1". The second (if present) would be named "C:\FNET\DIRM2". NOTE: Remember that each directory list meny file name must limited to 7 characters. This does not include the path. 5. This completes the upgrade to Feathernet version 3.9jß from version 3.9iß. IF you have not been running version 3.9iß you *MUST* ensire you have completed all previous upgrade instruction contained in this ----------------------------------------------------------------------------- Feathernet Bulletin Board Version 3.9iß 11 March 1991 o Fixed a problem with 'logon.txt' display at logon when running under a 'frontdoor' program. ----------------------------------------------------------------------------- Feathernet Bulletin Board Version 3.9gß 10 March 1991 o Rewrote the routines which write to 'caller.log' for each node. Now the caller.log file(s) are formatted in 64 byte records with the first 64 characters of each record being text and the last 2 characters being a CR/LF. o Rewrote the ARCVIEW routine which was causing some errors if a file was not actually on disk when the directory listing search method was used and the file was listed in the DIRxx file. o Rewrote the Upload Time Credit routine. It now gives proper credit. Note that a 1.00 time factor will just make the upload time not count against the caller's time. A factor of 2.00 would give the caller additional time equal to the time the upload had taken. o Added support for Viewing the 'caller.log' file both online and from the waiting for call screen. The command for viewing the log online is 'CALL' from the main menu. Obvious 'hot keys' will not work with this command. The log is viewed in reverse chronologigal order. o Modified the conference control file ('sigdata') to allow each conference to have a specific file directory control file (area). Different conferences may share a file control area if desired. There are 255 allowable file control files. Thus you may have up to 99 directories in each file control area. o Modified the file control area setup to include a data file to be used by 'fncfg' when editing or setting up the file control areas and conferences. The file 'dirmast.dat' contains one line of text up to 60 characters which describes the directory control area. This is to assist the sysop during editing of the configuration. o Created a utility called 'sigcvt.exe' whic MUST be run from each node directory before attempting to run this upgrade. This little program will modify the 'sigdata' file by adding a ", 1" to the 2nd line of each conference's entry in the file. You will need to run fncfg.exe and edit each conference configuration for which you do not want the first directory control file used. o Made a utility to 'fix' each node's 'caller.log' file. Run the program 'callfix.exe' from each node directory. It modifies the 'caller.log' to the correct record length of 64 bytes per entry. o Replace your old 'fnettext' file with the one in this archive. o Replace your old 'fnet.scr' file with the one in this archive. o There are other changes made but for now they are not so critical. ----------------------------------------------------------------------------- Feathernet Bulletin Board Version 3.9ß 03 March 1991 DISCLAIMER ---------- This is a *BETA* test version of the Feathernet code. Your use of it constitutes your full acceptance of any loss or damages whatsoever resulting directly or indirectly from use of this program. Further, you agree that Feathernet Software and Ron Pierce shall NOT be held liable for any damage or loss whatsoever which results from the use of this program. What's New ---------- Version 3.9ß allows the sysop to utilize more than one file directory control file. This is the file which contains the name, path, security levels to each file directory. Also the name, path, security level of alternate directory paths and the upload directory paths. Dir Control Files ----------------- In version 3.8 and earlier only one file held this file directory information: 'dirdata' Now you can specify more than one 'control' file The names of the various "control" files are held in a file named 'DirMAst' This file is located in the node directory for each node. The format for 'dirmast' is: 3 ; number of file directory "control" files dirlist1 ; Name of the first control file dirlist2 ; Name of second "" "" dirlist3 ; Name of third "" "" Installation ------------ 1. Make backups of the following files from version 3.6, 3.7, or 3.8: fnet.exe fncfg.exe dirdata fnet.scr 2. Copy the following fiies into each node directory: fnet.exe fncfg.exe dirmast fnet.scr 3. You can edit the directory "control" files with a text editor or use the 'fncfg.exe' file accompanying version 3.9ß. Ensure you use the same format "dirdata" uses if you edit the control file(s) with a text editor. 4. Create two text files for your users: DMAS.MEN ; ASCII listing of dir control files and description DMASG.MEN ; ANSI listing of dir control files and description Place these in each Node Directory ( you may have different setups for various nodes) 5. Run 'fncfg.exe' and verify or edit the various directory control files. 6. Now we must clarify the "DIRxx" (directory listing files) file naming conventions for version 3.9ß. Each "DIRxx" file for the first control directory ("dirdata") remains as is: 'dir1', 'dir2', etc. For each additional directory control file the filenames of the "DIRxx" files are names in the following manner. The name of the "DIRxx" files for the second control file are "DIR2_" plus the "xx" number: DIR2_1, DIR2_2, DIR2_3, etc The name of the "DIRxx" files for the third control file are "DIR3_" plus the "xx" number. DIR3_1, DIR3_2, DIR3_3, etc This continues by using the number of the control file (1 - 99) plus the underscore "_" character followed by the directory list file number. 7. This completes the conversion from version 3.6 - 3.8 to version 3.9ß. New command in the file transfer area for changing directory control files is (C). Add this to your file transfer menus. Good luck.